internal/config: replace viper with custom config loader #564
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
adambabik
force-pushed
the
adamb/replace-viper
branch
from
fc20cf6 to
4bca199
Compare
adambabik
force-pushed
the
adamb/replace-viper
branch
3 times, most recently
from
e938d2a to
fb67d70
Compare
sourishkrout
force-pushed
the
adamb/replace-viper
branch
from
fb67d70 to
f0e4c41
Compare
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR implements a generic config loader. The main purpose is to find all relevant
runme.yamlstarting from a Markdown file location. The algorithm goes up the directory tree until the project root. The next step is to merge all foundrunme.yamlconfigs into a single one that will be used by the execution layer.